Twelve Data

Created By
Twelve Dataa year ago
A Model Context Protocol server for the Twelve Data API. This server provides tools to fetch market data—historical time series, latest quotes, and instrument lists—for stocks, forex pairs, and cryptocurrencies.
Overview

what is Twelve Data?

Twelve Data is a Model Context Protocol server that provides tools to fetch market data, including historical time series, latest quotes, and instrument lists for stocks, forex pairs, and cryptocurrencies.

how to use Twelve Data?

To use Twelve Data, you can either run it directly using uvx or install it via pip. You will need to configure it with your API key to access the data.

key features of Twelve Data?

  • Fetch historical price data for various financial instruments.
  • Get the latest price quotes for stocks and forex.
  • List available stocks, forex pairs, and cryptocurrencies.

use cases of Twelve Data?

  1. Analyzing historical stock price trends.
  2. Fetching real-time forex quotes for trading.
  3. Compiling a list of available cryptocurrencies for investment.

FAQ from Twelve Data?

  • What types of data can I fetch?

You can fetch historical time series, latest quotes, and instrument lists for stocks, forex pairs, and cryptocurrencies.

  • Is there a cost associated with using Twelve Data?

Please check the Twelve Data website for pricing details and API usage limits.

  • How do I get my API key?

You can obtain your API key by signing up on the Twelve Data website.

Server Config

{
  "mcpServers": {
    "twelvedata": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.twelvedata.com/mcp/"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Twelve Data
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago